Repository navigation
Conversation
`Repository.RefreshCommits()` cancels the previous refresh, but the token was never passed to `QueryCommits`, so a superseded `git log` (and its follow-up `QueryCurrentBranchCommitHashes`) kept running to completion. During bursts of ref changes (fetching multiple remotes, rebasing) several of them could pile up. Pass the token to `QueryCommits` and terminate the running git process when it is cancelled (via a small `Command.TerminateOnCancellation` helper), skip the follow-up query once cancelled, and don't report errors caused by cancellation. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KCxH1zwDXLd9kfAAkcf6PZ
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Repository.RefreshCommits()cancels the previous refresh, but the token wasnever passed to
QueryCommits, so a supersededgit log(and its follow-upQueryCurrentBranchCommitHashes) kept running to completion. During bursts ofref changes (fetching multiple remotes, rebasing) several of them could pile up.
Pass the token to
QueryCommitsand terminate the running git process when itis cancelled (via a small
Command.TerminateOnCancellationhelper), skip thefollow-up query once cancelled, and don't report errors caused by cancellation.
🤖 Generated with Claude Code